| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-AS.4.3.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.4.3 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | AS_4_3_Support_for_Communications_Between_Organizations |
| Title | AS.4.3 Support for Communications Between Organizations (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Facilitate communications regarding patient orders, data and status between organizations. |
| Purpose | There needs to be an ability to communicate patient data and status (e.g., patient history, patient physical examination), discrete clinical data (e.g., blood pressure, pulse, temperature, pulse oximetry, laboratory data, microbiology data, radiology data), and orders(e.g., medications, tests) between health care organizations, particularly during patient transfers. This information may include items such as outstanding patient requests, clinician care recommendations, and outstanding treatment and workflow tasks for the patient. Organizations can include both health care providing organizations (e.g., hospitals, nursing homes) and non-health care providing organizations (e.g., funeral homes, disaster operations, employers). |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Facilitate communications regarding patient orders, data and status between organizations.
There needs to be an ability to communicate patient data and status (e.g., patient history, patient physical examination), discrete clinical data (e.g., blood pressure, pulse, temperature, pulse oximetry, laboratory data, microbiology data, radiology data), and orders(e.g., medications, tests) between health care organizations, particularly during patient transfers.
This information may include items such as outstanding patient requests, clinician care recommendations, and outstanding treatment and workflow tasks for the patient. Organizations can include both health care providing organizations (e.g., hospitals, nursing homes) and non-health care providing organizations (e.g., funeral homes, disaster operations, employers).
| AS.4.3#01 | dependent SHOULD |
The system SHOULD provide the ability to render patient transfer information to other health care organizations (e.g., hospitals, clinics, specialists, nursing homes) according to scope of practice, organizational policy, and/or jurisdictional law. |
| AS.4.3#02 | dependent MAY |
The system MAY provide the ability to render selected patient transfer information to non-health care organizations (e.g., funeral home) according to scope of practice, organizational policy, and/or jurisdictional law. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-AS.4.3",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Facilitate communications regarding patient orders, data and status between organizations.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>There needs to be an ability to communicate patient data and status (e.g., patient history, patient physical examination), discrete clinical data (e.g., blood pressure, pulse, temperature, pulse oximetry, laboratory data, microbiology data, radiology data), and orders(e.g., medications, tests) between health care organizations, particularly during patient transfers.</p>\n<p>This information may include items such as outstanding patient requests, clinician care recommendations, and outstanding treatment and workflow tasks for the patient. Organizations can include both health care providing organizations (e.g., hospitals, nursing homes) and non-health care providing organizations (e.g., funeral homes, disaster operations, employers).</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.4.3#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render patient transfer information to other health care organizations (e.g., hospitals, clinics, specialists, nursing homes) according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.4.3#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to render selected patient transfer information to non-health care organizations (e.g., funeral home) according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.4.3",
"version" : "2.1.0",
"name" : "AS_4_3_Support_for_Communications_Between_Organizations",
"title" : "AS.4.3 Support for Communications Between Organizations (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Facilitate communications regarding patient orders, data and status between organizations.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "There needs to be an ability to communicate patient data and status (e.g., patient history, patient physical examination), discrete clinical data (e.g., blood pressure, pulse, temperature, pulse oximetry, laboratory data, microbiology data, radiology data), and orders(e.g., medications, tests) between health care organizations, particularly during patient transfers.\n\nThis information may include items such as outstanding patient requests, clinician care recommendations, and outstanding treatment and workflow tasks for the patient. Organizations can include both health care providing organizations (e.g., hospitals, nursing homes) and non-health care providing organizations (e.g., funeral homes, disaster operations, employers).",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-AS.4.3-01",
"label" : "AS.4.3#01",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render patient transfer information to other health care organizations (e.g., hospitals, clinics, specialists, nursing homes) according to scope of practice, organizational policy, and/or jurisdictional law."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-AS.4.3-02",
"label" : "AS.4.3#02",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to render selected patient transfer information to non-health care organizations (e.g., funeral home) according to scope of practice, organizational policy, and/or jurisdictional law."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.